Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain v0 to v1 migration #2475

Merged
merged 1 commit into from
Nov 30, 2022
Merged

Conversation

carolynvs
Copy link
Member

What does this change

Include an explanation on the website and in the command doc on how the storage migrate command behaves. Warn people to not repeat the migration after they have used Porter v1 with the migrated database.

What issue does it fix

I realized that the migration behavior wasn't documented when I was helping a user with their migration.

Notes for the reviewer

N/A

Checklist

  • Did you write tests?
  • Did you write documentation?
  • Did you change porter.yaml or a storage document record? Update the corresponding schema file.
  • If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Reviewer Checklist

  • Comment with /azp run test-porter-release if a magefile or build script was modified
  • Comment with /azp run porter-integration if it's a non-trivial PR

Include an explanation on the website and in the command doc on how the storage migrate command behaves. Warn people to not repeat the migration after they have used Porter v1 with the migrated database.

Signed-off-by: Carolyn Van Slyck <[email protected]>
@carolynvs carolynvs marked this pull request as ready for review November 30, 2022 14:54
@carolynvs carolynvs merged commit ed6fd65 into getporter:main Nov 30, 2022
@carolynvs carolynvs deleted the repeat-migration branch November 30, 2022 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants